Contracts                                                                                           

The Contract Management product in the GEP QUANTUM suite brings together procurement, legal, sales and other stakeholders across the contract life cycle in one intuitive, easy-to-deploy contract administration, management and compliance solution. It allows you to author, collaborate, and aggregate contracts in a central repository for effective contract compliance, administration, and utilization.

In this release, 06 features/enhancements have been added to Contracts.

Ability to Capture SOEID of BAO and BAO Support

PRJCT-10447 | Configurable: No

Customer: CITI

With this release, the application now captures the SOEIDs (Client Contact Code) and full names of active users in the Aravo Details section under the BAO and BAO Support columns, ensuring clearer visibility and traceability of role assignments.

Copy Related Content Linkages from Live Contracts to Modification Copies

PRJCT-10400 | Configurable: Yes

Customer: CITI

With this release, related content linkages (Project, PRF, RFX, Contract Request, Requisition, Invoice, Service Confirmation, PO) from a live Contract are copied to its modification copy, ensuring that modifications retain the original relationships for reference and continuity.

Configuration Details:

  • Setting Name: copy_related_content_to_modification

  • Possible Values: True/False

  • Required Value: True

  • Default Value: False

Auto-Populate Approval Data in Contract Language

PRJCT-10295 | Configurable: No

Customer: CITI

With this release, approval details of the last approver for both Service Provider and Service Recipient are now automatically populated in a table within the Contract language. This eliminates manual entry and ensures that key sign-off information is accurately reflected in the Contract document.

Introducing NCOC Integration for E-Signature on Contracts

PRJCT-9154 | Configurable: Yes

Customer: NCOC

With this release, you can send Contract documents for signature using the NCOC Integration, enabling seamless e-signature management. This allows you to define document types and track signature statuses directly within the application. It supports managing revocation and rejection workflows, ensuring that the entire Contract signing process is streamlined, compliant, and fully traceable end-to-end.

Pre-requisite: NCOC e-sign integration has to be set up at the platform e-sign end.

Configuration Details:

  • Setting Name: EnableNCOCE-Sign

  • Possible Values: True/False

  • Required Value: True

  • Default Value: False

 

Default Signing Order for ‘Send for E-Sign’ Page

PRJCT-10355 | Configurable: Yes

Customer: Jefferies

With this release, you can default the signing order on the Send for E-Sign page. The Contracts are routed first to the Internal Party and then to the External Party, ensuring compliance with Jefferies’ workflow requirements. This eliminates the need to manually reorder recipients each time while still allowing flexibility when required.

Configuration Details:

  • Setting Name: Default Signatories Signing Order

  • Possible Values: True/False

  • Required Value: True

  • Default Value: False

Enhanced Email Notification for Termination Approval

PRJCT-10291 | Configurable: Yes

Customer: AWR, NEOM, WPP

With this release, when a termination request is sent for approval, the email notification now includes a summary detail in the following tabular format:

Status

Level & Step Details

Name

Comments

Actions Taken On

<Submitted>

OR

< Pending/Approved/Rejected

/Recalled >

<Level N> | <Step No> | <Step Name>

<Submitter User’s Name>

OR

< Approver’s Name>

<Sent For Termination Approval Comments>

OR

<Approval/Rejection Comments>

<Date and Time in user’s regional format>

Key Details:

  • Submitter details appear first, followed by approvers in chronological order.

  • Status shows Submitted for the submitter, and Termination Approval Pending/Approved/Rejected for approvers.

  • Action Taken On is displayed in the recipient’s locale date & time format.

  • Notifications are triggered based on the approver’s action, as shown below:

Notification Code

Event Code

Event Name

Termination Approval Fully Approved

CLM-101-TerminationApprovalsFullyApproved

Termination Approval Fully Approved

Termination Approval Rejected

CLM-101-TerminationApprovalRejected

Termination Approval Rejected

Termination Approval Recalled

Termination Approval Recalled

CLM-101-TerminationApprovalRecalled

Termination Approval Recalled

Configuration Details: The availability of this feature is based on the Notification Engine and Rule Engine settings. Please reach out to your Account Manager for more information.